| Author |
Thread Statistics | Show CCP posts - 6 post(s) |
Captain Thunk
Sniggerdly
Pandemic Legion
124
   |
Posted - 2012.09.19 15:01:00 -
[1] - Quote
CAKs fail to encompass the abilities of its predecessor the legacy API key.
A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.
This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.
There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it. |
Captain Thunk
Sniggerdly
Pandemic Legion
124
|
Posted - 2012.09.19 15:15:00 -
[2] - Quote
Promiscuous Female wrote:Captain Thunk wrote:CAKs fail to encompass the abilities of its predecessor the legacy API key.
A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.
This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.
There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it. read: "Even though months and months have passed I have been too lazy to update our software; now that the plug is getting pulled I am shi tting myself continuously at the prospect of having to rewrite all my code in the span of 2 weeks"
It takes about 3 lines to make use of new keys. The reason I haven't done so is because, guess what, like I said in my first post - CAKs are not as good as a full legacy key.
|
Captain Thunk
Sniggerdly
Pandemic Legion
126
|
Posted - 2012.09.19 16:33:00 -
[3] - Quote
Promiscuous Female wrote:Captain Thunk wrote:Promiscuous Female wrote:Captain Thunk wrote:CAKs fail to encompass the abilities of its predecessor the legacy API key.
A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.
This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.
There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it. read: "Even though months and months have passed I have been too lazy to update our software; now that the plug is getting pulled I am shi tting myself continuously at the prospect of having to rewrite all my code in the span of 2 weeks" It takes about 3 lines to make use of new keys. The reason I haven't done so is because, guess what, like I said in my first post - CAKs are not as good as a full legacy key. your fault for writing code that relies on a goofy edge case instead of developing a proper application fortunately for you they aren't actually shutting down old keys, just making it impossible to generate additional legacy keys, so you probably got another couple of months before you have to get off your ass and change "3 lines" of code
I did the changes 12 months ago, I simply disabled it because instead of asking for multiple keys and doing the necessary checking to make sure all have been entered I could just stick to 1 legacy key as it's just much better.
It was originally written when CAK didn't exist, so your spouting about "developing a proper application" is just stupid nonsense being spewed by a kid who just collected his Basic Computing certificate last week. Shutting down legacy API at this juncture serves no purpose other than to supply reason for a devblog. It's a system that happily runs itself and no-one is planning on adding anything to the API or working on it in any manner as all efforts are concentrated on CREST.
My only crime is that I am one of the few people who actually use all of the available API which is why hoopleheads such as yourself keep spouting rubbish about "should have updated" oblivious to the limitations that CAK pose compared to their predecessor. |
Captain Thunk
Sniggerdly
Pandemic Legion
127
|
Posted - 2012.09.19 17:36:00 -
[4] - Quote
Promiscuous Female wrote:
that's an awful lot of :words: for "i'm too lazy to update my application"
also i guess you missed the locations, charactername, and contracts api stuff that they added after announcing crest
I remember back when Goons could troll well 
Now it's all generic paint-by-numbers nonsense.
|
Captain Thunk
Sniggerdly
Pandemic Legion
127
|
Posted - 2012.09.19 17:48:00 -
[5] - Quote
You like posting don't you?
I can tell. |
Captain Thunk
Sniggerdly
Pandemic Legion
129
|
Posted - 2012.09.20 08:50:00 -
[6] - Quote
Golden Gnu wrote:
jEveAssets already moved to CAKe, but, I still get people who can not figure out they need a separate corporation key.
This is the problem (not the altering of code).
Explaining to people that they've just entered a key but it's detected that it needs more just to maintain the same level of service they are used to with Legacy keys.
And you have to check the validity of the key on every use because the user might have gone back to the Eve website and changed the privileges for the key.
|
| |
|